can't we use LTarget,Operand,RTarget which is way more natural to scan

also, how do you add multiple constraints? using ; as sep?

does it also work (if at all) for distinct_hosts?

if Operand is distinct_host the [https://www.nomadproject.io/docs/http/json-jobs.html](nomad json docs) says When specified, LTarget and RTarget should be omitted.

and distinct_property says When specified, LTarget should be the property that should be distinct and and RTarget should be omitted.

using comma may interfere with set_contains with assume RTarget is a comma separated list of values

Agree, LTarget,Operand,RTarget looks better. Multiple constraints at the moment are separated automatically:

1,=,2,3,=,4
Makes two constraints: 1=2 and 3=4

This currently will not work for distinct_host because I am automatically wrapping the LTarget with ${ } as Jenkins does not let you input these characters into a text field easily. I will change the code so LTarget is blank if not specified, this would allow distinct_host to work if you did something like:
Input: ,distinct_host,
However, this would not fix the distinct_property problem as it requires an LTarget (which will automatically be wrapped with ${ }), unless I use an if statement to check for distinct_property, but that is not very future-proof

Good point on the comma, I should use a different delimiter. It is hard to decide the "best" way to input the data into the field, as the three main challenges are:

1.) Need to input N groups of 3 items in a single textbox
2.) Textbox filters out certain characters (i.e. ${}, which Nomad requires in the LTarget for certain constraints)
3.) Cannot use comma as a separator

I'll wait a few days to see If there are some good suggestions for how to input the text into this field, I can implement them. Otherwise, I'll go ahead and come up with something on my own (might not be very user friendly or intuitive, though.)

ltarget,operand,rtarget|ltarget,operand,rtarget
ltarget,operand,rtarget/ltarget,operand,rtarget
ltarget,operand,rtarget:ltarget,operand,rtarget
ltarget,operand,rtarget#ltarget,operand,rtarget

is my suggestions, not sure if they are brilliant, the best would be to have a line per constraint, can jenkins do multiple inputs ? |,/, :, #

Well the commas interfere with set_contains, maybe it would be better to do something like:
ltarget operand rtarget|ltarget operand rtarget
I also need to find some way to be able to deal with ${ } as well, I will take a look again to see if its possible to accept the input for ${ } directly in the textbox, or maybe prepend ltarget with a character such as - to allow the expansion to happen, and to keep things somewhat future-proof.
Spaces are not really a great separator either in the case of ltarget or rtarget being omitted